-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Primitive fixes; docs, dev checks, cleanup; depth fail, rtc, hardware resources #8044
Conversation
Thank you so much for the pull request @nmschulte-aviture! I noticed this is your first pull request and I wanted to say welcome to the Cesium community! The Pull Request Guidelines is a handy reference for making sure your PR gets accepted quickly, so make sure to skim that.
Reviewers, don't forget to make sure that:
|
Please see also #7947 (doc updates). |
We have a signed CLA from Aviture for username Was there an open issue for this bug? If so, can you link it? If not, can you provide a Sandcastle example of the bug this PR fixes, to make this easier to review? |
I operate both usernames, @nmschulte and @nmschulte-aviture. If I need to amend the CLA somehow that is fine; if I simply need to voice approval as @nmschulte I can do that as well.
I do not know of any open issues addressing these concerns. I can create a test/example case for the rtc This command should show that the |
The above example also seems to show a problem with |
Thanks @nmschulte-aviture! This looks good. I'll merge as soon as CI passes |
Thanks for the awesome work @nmschulte-aviture! Your contribution is about to launch to millions of users with the next release. 🚀 Do you mind if we tweet about it? CC @OmarShehata @slchow. |
Some cleanup to
Primitive.js
.CLA is signed and
CONTRIBUTORS.md
is already updated:https://github.com/Aviture/cesium/blame/primitive-fixes/CONTRIBUTORS.md#L69